CA ARCserve® D2D r16 Update 5 Release Notes
1.0 Welcome
2.0 Enhancements
3.0 Issues Fixed
4.0 Known Issues
5.0 Limitations
6.0 Installation
6.1 Prerequisite Tasks
6.2 Installation Instructions
7.0 Contact Arcserve
1.0 Welcome
Welcome to the CA ARCserve D2D r16 Update 5 Release Notes.
This Release Notes contains important information about
this update.
2.0 Enhancements
The following enhancements have been added to CA ARCserve
D2D for this update:
- UEFI (Unified Extensible Firmware Interface) Support--UEFI
is a firmware interface that Windows Vista SP2 (x64),
Windows 2008 (x64), Windows 2008 R2, and Windows 7 (x64)
supports. CA ARCserve D2D includes the following UEFI
Support:
- Computers that adhere to the Extensible Firmware Interface
(EFI) use the EFI System Partition, which is a partition on
a data storage device. The EFI System partition is critical
for Bare Metal Recovery (BMR). Therefore, when you select
boot volume "C" on a UEFI system, the EFI System Partition
is selected automatically for the backup source for BMR and
an information message is displayed.
- To perform BMR for a UEFI system, you must boot the
computer in UEFI mode. BMR does not support restoring a
computer with different firmware.
- Mount Recovery Point--Provides the ability to mount a
recovery point to a drive letter (volume) or an NTFS
folder, to view, browse, copy, or open the backup files
directly in Windows Explorer.
- Application Recovery Support--CA ARCserve D2D now supports
Microsoft SQL Server 2012 Express/Web/Standard/Business
Intelligence/Enterprise.
3.0 Issues Fixed
This update fixes the following issues:
- A problem that causes the debug log files not to display
backup status messages. (Test Fix T2D2864)
- A problem that causes an Exchange granular-level restore to
fail when the number of tagged values exceeds 8192 and a
message displays in the ExchangeReader.dll log. (Test Fix
T2D2871)
- A problem that causes the date to display incorrectly on
the CA ARCserve D2D Home Page in the Italian version of CA
ARCserve D2D r16. (Test Fix T36A739)
- A problem that causes the transaction logs to fail to purge
when CA ARCserve D2D is used to back up Microsoft SQL 2008
and the Advanced Backup Settings Truncate log field is set
to Daily. (Test Fix T36A740)
- A problem that causes future verify or incremental backups
to fail continually because of data corruption in the
backup due to various reasons, including bad sectors on the
destination disks. After you apply this fix, perform the
following tasks or note the following information:
- Back up the corrupted blocks from the backup source again
by running a new verify backup job.
- After this new verify backup is complete, you can perform
the following tasks:
- Continue to run incremental backup jobs successfully.
- Restore or perform BMR from the recovery points which are
generated after the new verify backup.
- The new verify backup does not recover the corrupted blocks
that were previously generated.
(Test Fix T5E5127)
- A problem that causes a session purge to fail after a
merge. This failure usually happens when backing up to a
remote location. The purge fails because the deleted folder
failed with error code 145 "The directory is not empty."
(Test Fix T5E5146)
- A problem that causes a CA ARCserve D2D r16 backup job to
stop responding when taking a snapshot. This problem would
usually happen when Microsoft SQL Server Express is
installed and the following two default instances exist at
the same time:
- Microsoft SQL Server default instance MSSQLSERVER
- Microsoft SQL Server Express default instance SQLEXPRESS
(Test Fix T5E5147)
4.0 Known Issues
The following issues are known to exist in this update:
- A backup can fail when you have duplicated machines backing
up to the same remote shared folder.
Symptom
This issue occurs when the source system is configured to
do a backup to a remote shared folder and a bare metal
recovery (BMR) is performed to a destination machine. After
BMR, if the source system is still running, two machines
with the same hostname will perform the backup to the same
destination. If this duplication occurs, the backup can
fail or the backed up data can be corrupted.
Solution
If you are testing BMR, unplug the cables before you
reboot. Otherwise, after you perform BMR and you reboot,
duplicate machines will exist on your domain.
- A UEFI system with logical partitions cannot reboot after
BMR.
Symptom
This issue occurs when a Windows 7 or Windows 2008 R2 UEFI
system has a logical partition on the system, and after you
perform BMR the machine fails to reboot.
Solution
Refer to the following Microsoft knowledge base article to
understand how this known issue occurs and how to resolve
it. Apply the fix before performing the backup with CA
ARCserve D2D.
http://support.microsoft.com/kb/982929
- A database with special characters is not displayed in the
Restore user interface.
Symptom
If the Microsoft SQL Server database name contains a
backslash ("\"), after performing a backup using the CA
ARCserve D2D database whose name contains a "\" is not
displayed in the Restore user interface. An issue exists in
the cataloging modules which does not support a "\" in the
database name.
Solution
Actually the database is backed up properly and you can use
the Mount Recovery Point feature to find and copy the
database files manually.
- A reboot can be required when upgrading from CA ARCserve
D2D r16 Update 4 to CA ARCserve D2D r16 Update 5.
Symptom
For Windows 2003 and Windows XP systems, rebooting the
machine can be required after upgrading to CA ARCserve D2D
r16 Update 5 if Explorer Extension is used. Windows
Explorer occupies some of the binaries and they cannot be
replaced.
Solution
After the upgrade is complete, reboot the machine.
- During the CA ARCserve D2D BMR driver injection phase, a
warning message displays the Windows Vista operating system
for all target operating systems and can be ignored.
Symptom
When BMR detects a driver but cannot ensure that the driver
is compatible with the target operating system, a warning
message displays asking you to confirm. This confirmation
is to avoid inserting a wrong driver to the target system
which can cause the machine to fail to boot.
Solution
If you are sure the driver works for the system being
recovered, select Yes and BMR continues to insert the
driver to the system being recovered.
5.0 Limitations
The following limitations are known to exist in this update:
- Recovering BIOS-based systems to UEFI-based systems and
recovering UEFI-based systems to BIOS-based systems are not
supported.
- After CA ARCserve D2D r16 Update 5 is installed, to migrate
CA ARCserve D2D backups successfully to tape using CA
ARCserve Backup r16 SP1, apply the patch RO45010 on top of
the RO40595 patch on all the CA ARCserve D2D servers
where CA ARCserve Backup r16 SP1 Server/CA ARCserve Backup
r16 SP1 Client Agent is installed.
6.0 Installation
The following sections provide information about
installation prerequisites and installation instructions.
6.1 Prerequisite Tasks
Before you install this update, verify that CA ARCserve D2D
r16 is installed (with or without any previous r16 Updates).
6.2 Installation Instructions
You can use two methods to install this update:
7.0 Contact Arcserve
Contact Arcserve Support
For your convenience, Arcserve provides one site where you
can access the information that you need for your Home
Office, Small Business, and Enterprise Arcserve products.
At http://arcserve.com/support, you can access the
following resources:
- Online and telephone contact information for technical
assistance and customer services
- Information about user communities and forums
- Product and documentation downloads
- Arcserve Support policies and guidelines
- Other helpful resources appropriate for your product
Providing Feedback About Product Documentation
If you have comments or questions about Arcserve product
documentation, you can send a message to techpubs@arcserve.com.
Copyright © 2012 Arcserve. All rights reserved. All
trademarks, trade names, service marks, and logos
referenced herein belong to their respective companies.